The adapter fails when the request targets a non-presence container that exists but its children do not; ConfD would generate an empty JSON document that is not processed correctly - this is fixed. The question is whether an empty update or no update at all should be returned in such case. The implementation goes with the former with the following reasoning:

• we return no update if the path simply does not exist, so it makes sense to behave differently here;
• the specification seems to require that in GetResponse Behavior Table.